A discussion similar to this one is here: Related discussion. This learning was derived by a 3. Sometimes, I find that there isn't a lack of shared knowledge as much as there is a lack of either hashtag usage or indexing the topics, so hopefully I've entered enough tags to help reach more people. I have a new implementation of Enterprise GIS After publishing about services through a python script against Arc Map MXD documents, the server would refuse to publish any more, or would get to various states of publishing it wasn't consistent between SDDraft creation, Staging or uploading and throw some error s to the log see below and then hang.
I thought my server was just slow, so I waited.. The server was unable to create a GIS service instance. The exact cause is unknown. Please contact Esri Support for further assistance and provide the following information. I also got the following errors, which also weren't consistent between publishing attempts, but did recur frequently in my troubleshooting efforts:. XML Parser initialization failed.
If you research XmlSupport. I compared that file downloaded from the article against the The first thing I noticed is that my file had not been updated since more than a year before, so I made a quick assumption that since no change was made very recently, the file was not corrupted by something I had done I'm pretty sure in some cases, it could be corrupt, but I couldn't think of any off the top of my head.
I opened up the file for editing and the content looked ok-- nothing garbled this is a very readable file. Having said that, the old and new files are vastly different. I decided to keep looking. While this is noted as a generic error, it was an indicator that only part of the publishing process could be complete-- apparently, in my case, the server reached its maximum processing capacity and just stopped.
Some history on our upgrade: One of the reasons we decided to "re-architect" our structure and upgrade to From the related article top of this discussion , you can read about some of the things that Windows Server will do to "assist" you when you hit the wall-- memory swapping, for instance, but these activities still don't preclude the server from becoming "unstable" when run at that capacity. Something important I learned: adding servers to a site only spreads processing capabilities spreads the work out AFTER the service gets published between the different machines in the Server Site aka horizontal scaling or scaling out.
